home *** CD-ROM | disk | FTP | other *** search
- Path: sascha.esrac.ele.tue.nl!leon
- From: leon@esrac.ele.tue.nl (Leon Woestenberg)
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: OS features
- Date: 10 Jan 1996 12:24:06 GMT
- Organization: Eindhoven Student Radio Amateur Club
- Message-ID: <4d0b56$gga@tuegate.tue.nl>
- References: <92747544038@PAPA.NORTH.DE> <4b3h9s$1st@alterdial.UU.NET> <2152.6561T63T2136@cycor.ca> <4b7i18$si1@vixen.cso.uiuc.edu> <oj6raxxrr0o.fsf@hpsrk.fc.hp.com> <13213431@sourcery.han.de> <4cp0un$cve@serpens.rhein.de>
- NNTP-Posting-Host: sascha.esrac.ele.tue.nl
- X-Newsreader: TIN [version 1.2 PL2]
-
- Michael van Elst (mlelstv@serpens.rhein.de) wrote:
-
- : Separated address spaces for each process are even better because
-
- I personally see this as the most optimal solution, but my view may be
- limited on this.
-
- : the total address space now grows with the number of processes. But
- : this approach costs a lot in compatibility. It might be possible
- : to use partially separated adress spaces though in new programs.
-
- Where does it break compatibility? (And do you mean compatiblity with
- programs not using the MEMF_PUBLIC flag, or all current programs?).
-
- Leon Woestenberg.
-
-